|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards track RFC approved November 2001.
|
|
3.
|
Justification for the specific reference:
|
|
|
Continua requires the use of this RFC, Reliable Delivery for Syslog, for the robustness and security in message delivery over the WAN Interface. The BSD Syslog Protocol describes a number of service options related to propagating event messages. For example, there are two mappings of the syslog protocol to TCP connections, both useful for reliable delivery of event messages. One is a trivial mapping maximizing backward compatibility and the second provides a more complete mapping. Both provide the degree of robustness and security required by Continua in message delivery that is unavailable to the usual UDP-based syslog protocol, by providing encryption and authentication over a connection-oriented protocol. Utilized within many H.810-compliant WAN devices certified by Continua Health Alliance.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
N/A.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard RFC approved November 2001 and its is widely used
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
See 6. above.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
N/A.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Lonvick, C., "The BSD Syslog Protocol", RFC 3164, August 2001./
/
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. /
/
[3] Rose, M., "The Blocks Extensible Exchange Protocol Core", RFC 3080, March 2001./
/
[4] Rose, M., "Mapping the BEEP Core onto TCP", RFC 3081, March 2001./
/
[5] Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782, February 2000./
/
[6] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996./
/
[7] Alvestrand, H., "Tags for the Identification of Languages", BCP 47, RFC 3066, January 2001./
/
[8] Leach, P. and C. Newman, "Using Digest Authentication as a SASL Mechanism", RFC 2831, May 2000.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
N/A.
|
|
